Base Solana Bridge Guide #437
Conversation
✅ Heimdall Review Status
|
|
Review Error for kmk142789 @ 2025-10-06 14:32:37 UTC |
| ## How it works | ||
|
|
||
| ### On Base | ||
| The Base bridge contract locks or burns tokens when sending messages to Solana, |
There was a problem hiding this comment.
We say "locks or burns" and "mints or unlocks"
Is it truly either? Or are we using these words as synonyms? If its just synonyms we should pick a single word. I think "lock" and "unlock" are the most immediately understood by the widest audience
There was a problem hiding this comment.
it's either, and it depends if the token is native to base (locks) or native to solana (burns) - I'll clarify it though, thanks
There was a problem hiding this comment.
Added callouts to clarify
There was a problem hiding this comment.
A broader preference of mine would be to move the "how it works" section below the implementation sections. And then in the implementation sections, we could have an internal link to the how it works section, something like "Read here to learn more about how the solana <>Base bridge works"
This focuses the doc on implementation and our general goal of shortening time to implementation, while still ensuring that the way the bridge works is documented
I would generally agree once we have clearer and easier paths towards integration (SDK), but I think in this case, it is unfortunately hard to start implementing without a basic understanding of how the bridge works - as it's a still a bare-bone smart contracts protocol and any developer would have to interact with the contract directly |
What changed? Why?
Adding a guide for developers using the new Base <> Solana bridge